Impressive work, @mrwogu! This is a substantial integration and the PR description is excellent — the Claude Code vs Factory AI comparison table is especially helpful. A few observations:

What looks good:

• The adaptation table clearly documents every difference between the two platforms and how each is handled.
• The plugin structure (gitnexus-factory-plugin/) is well-organized with proper manifest, hooks, MCP config, and skills.
• The hook logic in gitnexus-hook.js is defensive — it checks for the .gitnexus index, validates tool names, and has graceful fallback from direct binary to npx.
• Skills are comprehensive and well-written with clear workflows and examples.
• The .gitignore additions for Factory-specific files are correct.

Issues / suggestions:

1. Hook uses Execute but hooks.json matcher also lists it — The extractPattern function handles Grep, Glob, and Execute. For Execute, it only fires when the command contains rg or grep. This is smart, but the regex /\brg$/ with $ anchor might not match rg mid-path (e.g., /usr/bin/rg). Consider using just \brg\b (which you already use in the earlier test). Same for \bgrep$.

2. Timeout mismatch — hooks.json sets a 10-second timeout, but the npx fallback in the hook script has a 15-second spawnSync timeout. If the hook runner kills the process at 10s, the 15s inner timeout is never reached. You might want to align these (e.g., hook timeout at 20s, or npx timeout at 8s).

3. Skills content duplication — The 7 skills in gitnexus-factory-plugin/skills/ appear to be near-copies of the Claude Code skills in .claude/skills/. Long-term this creates a maintenance burden. Consider whether the setup script could generate/symlink these from a single source of truth. Not a blocker for this PR, but worth noting.

4. setup.ts and ai-context.ts changes — These look correct. The parallel installation to both .claude/skills/ and .factory/skills/ is straightforward. One thing to verify: does installFactoryHooks() handle the case where .factory/ doesn't exist yet? I see mkdirSync with recursive: true in the setup code, which should cover it.

5. Plugin author attribution — The plugin.json lists you as the author, but the homepage/repository point to the main GitNexus repo. This seems appropriate for a first-party plugin contributed upstream.

6. The shell hook (post-tool-use.sh) — Nice to have as a reference implementation, but make sure it's not also registered in hooks.json (it isn't — only the JS hook is). The shell version uses jq which may not be available everywhere. A note in the file header about this being an alternative would help.

Overall this is high-quality work with good attention to platform differences. The main actionable items are the regex fix and the timeout alignment.